perm filename LISP.BUG[RLL,DBL] blob
sn#644408 filedate 1982-03-02 generic text, type C, neo UTF8
COMMENT ⊗ VALID 00002 PAGES
C REC PAGE DESCRIPTION
C00001 00001
C00002 00002 ∂01-Mar-82 1739 Steve Crocker <Crocker at USC-ISIF> Re: MAPHASH problems in Interlisp??
C00004 ENDMK
C⊗;
∂01-Mar-82 1739 Steve Crocker <Crocker at USC-ISIF> Re: MAPHASH problems in Interlisp??
To: Masinter at PARC-MAXC, KINI at USC-ISIB
cc: InterlispSites↑ at PARC-MAXC
In-Reply-To: Your message of 1-Mar-82 1309-PST
An alternative strategy is not to use MAPHASH at all. An auxiliary
list may be kept, suitably updated whenever items are added to or deleted
from the table.
If this sounds ridiculously expensive, I submit that it competes with the
proposed solution for some frequencies of MAPHASHing, adding, deleting and
accessing elements.
It would be interesting to see the crossover point.
Steve
-------
∂02-Mar-82 1612 Dave Dyer <DDYER at USC-ISIB> Re: MAPHASH problems in Interlisp??
To: Masinter at PARC-MAXC, KINI at USC-ISIB
cc: InterlispSites↑ at PARC-MAXC
Interlisp-VAX shares exactly the same problem, except
that GC is much less frequent and therefore less likely to
occur in a critical interval.